Buy this Domain

Community Discussions

Explore the latest discussions and community conversations related to this domain.

How to print/cout to console char8_t, char16_t an char32_t characters in Visual Studio 2022?

Main Post:

Hi, to provide some context, I recently started reading the book "Beginning C++20 From Novice to Professional | Sixth Edition " by Ivor Horton and Peter Van Weert.

As the title says, in Visual Studio 2022 how do I print to the console char8_t, char_16_t and char32_t?

I ́ve been searching on Google for some hours now and the only somewhat usefull info I was able to found is that Windows uses mainly wchar_t which is fine to use on Windows but if I want to make a cross-platform application, the use of char8_t, char16_t, char32_t is a better practice.

This is what I tried to compile (aside from many variations) but didn ́t work.

import <iostream>; int main() { char8_t ch1{ u8'a' }; char16_t ch2{ u'a' }; char32_t ch3{ U'a' }; std::cout << ch1; std::cout << ch2; std::cout << ch3; }

I ́ve set C++ in Visual Studio to "Preview - Features from the Latest C++ Working Draft (/std:c++latest)".

As you can see I ́m using modules (import) instead of headers (#include) but this didn ́t give me any problem for the basic stuff I ́m doing so far and using headers didn ́t solve anything.

If it ́s some kind of weird (for a noob like me) workaround to make it work, I ́ll just use wchar_t (which also gave me some problems as I didn ́t know about "std::wcout") and come back to this issue when a have more experience.

Thank you very much in advance for any help you can provide.

EDIT: Thanks everybody for clarifying this a bit for me. This issue is beyond my knowledge at the moment and even worse given that, as I understand it, it isn ́t properly addressed by platforms for now.

I ́ll stick with "char" and "wchar_t" until I need to use other types. I ́ll tag this post as SOLVED, again, thanks everybody for the help :)

Top Comment: For cross-platform it is best to stick with UTF-8 encoding for your strings. On Windows that means changing the console's output code page.

Forum: r/cpp_questions

T shirt designs in Clip studio?

Main Post:

Is it possible to design t-shirt designs and other merchandise in clip art studio? If so any tutorials or guides?

Top Comment:

Anything you can design in photoshop you can also design in clip studio as the tools and functions are pretty much identical. So any tutorials you find in photoshop for t-shirt designs will probably be good enough to get you going. But its worth pointing out that I'm pretty sure most people design stuff like t-shirts in programs like illustrator, so thats probably where you will see the most tutorials for what you are looking for. I'm not a product designer so I can't recommend any tutorials.

Forum: r/ClipStudio

Why can't Tofiga Fepulea'i make it to the studio for Season 5?

Main Post:

They made it sound like he was going to miss all the episodes.

  1. Got an overseas gig?
  2. Doesn't like Jeremy Wells?
  3. Something else?

Top Comment: Sick

Forum: r/TaskmasterNZ

Studio One 7 - general feedback (not a rant)

Main Post:

I wanted to share a few thoughts on version 7, some ideas on how to make Studio One better (imho).

Let me preface this by saying I'm a huge fan of Studio One. It does a lot of things right and there's a big reason why it's my primary DAW. I want Studio One to always win. I want the guys at Presonus to win. I want the Studio One community to have the best DAW which translates our ideas into great results and doesn't stand in the way or kill our creative flow with odd things or weird little workflow issues.

The update is honestly somewhat lackluster, and I know I'm not the only one saying this. Some may disagree and that's fine. There are so many things, workflow improvements, Presonus could have done to enhance the usability and I'm all about the UX. So many little things they could have done to fix and improve stuff that's already in Studio One, but they decided to add new features instead - none of which (imo) are worthy of being flagship additions to a major version release (and some seem somewhat gimmicky tbh).

Not to mention Presonus-Fender went all 'corporate' with the pricing model. I mean, we already kind of did receive somewhat regular (even if unscheduled) point updates with useful new features and/or important fixes. On a 2-year release schedule (or something like that). Now it's $150 for a year worth of unannounced updates. That's all I'm going to say about this. Let's move on.

  1. The browser is detachable now. Great, but I'm not sure if I'm ever going to care about that. I definitely would care about a keyboard shortcut to preview a sound in the browser as many times as I want, without having to go up or down the list just to trigger the preview again (or having to use a mouse to stop and resume playback). FL Studio's browser does it right - I can press the the up/down arrow keys to scroll through the list quickly and press the right arrow key to audition my samples as many times as I want. Especially useful in case of drums and percussion - I can test out, in real time, different patters with different one-shots, while my music is playing. The loop and in-tempo playback are great features - for loops. The audition keyboard shortcut would be even better with additional midi keyboard support.
  2. Since version 4 (which is when I started using Studio One), they still haven't fixed the issue with the otherwise friggin' brilliant MixFX engine: it bypasses mixer channels which receive sidechain input from other channels within the same bus. For example, if you have CTC-1 on the Master Out, and a kick and a bass sidechained together, only one of those will be affected by CTC-1 which doesn't make sense - I want channels which are sidechained together to also be treated with the MixFX plugins. A kick and a bass is a simple problem to fix - can be routed to separate busses. But if you have a lot of channels which are sidechained to each other (and sidechaining is otherwise done perfectly in Studio One), then there's a problem. Creating busses as a workaround is a bandaid solution, not a permanent fix. I've been asking Presonus to look into this for years and it hasn't even been acknowledged.
  3. Middle-mouse (or the 'scroll wheel button') support for panning/moving around the arrangement window - like FL Studio does it (again, sorry), and many other modern creative software suites do it (Adobe, Affinity, DaVinci Resolve, Blender, etc.). It's just so much faster and more intuitive to move around the arrangement with the mid-mouse button. At least as an option to tick somewhere in the settings, so that those who care more about the mid-mouse tool selector menu can keep it as is (although attaching it to a modifier key, e.g., CTRL/CMD + MID-MOUSE would be a better solution, IMHO).
  4. An ability to use the scroll-wheel in the piano roll to change the grid resolution while painting notes across the grid. The toolbar in Studio One and the ability to use the scroll wheel on it is amazing, but we need to move away from the piano roll itself every time we paint notes in, just to change the resolution, which is not ideal. Imagine painting in an intricate pattern of hi-hat notes, which changes from 1/4 to 1/16 to 1/32 and with triplets of different values everywhere in between. It's not the biggest deal to navigate away from the piano roll to the toolbar to change the note resolution, but doing that every time we need to change it is killing the workflow. It's one of those little unnecessary things that kill the creative juices. I like to work fast and this is one of those things which slow me down. What I love about Studio One is the user experience, but in several aspects it's lacking (this being one example).
  5. An option to keep the note length of a previously inserted or selected note in the piano roll would be great, so that newly clicked-in notes don't have to be resized while working on the same part.
  6. We need an option that "burns" midi data on midi generators - e.g., on Scaler 2, arpeggiators, Reason rack, etc. If a midi tool generates different midi data based on my notes or chords, I'd like to be able to "apply" the generated data and have it as actual, new midi notes. Currently, I believe, it's only possibly to live-record midi to another midi track. Not ideal. FL Studio has a "Burn to Midi" option. Lovely. It's okay to borrow actually good UX solutions from other software to make your software even better for your user base, Presonus.
  7. The audition tool, "Listen Tool" in the piano roll currently starts playback of the whole part from where we click in the arrangment and continues till the end. For those of us who click in or paint in notes in the piano roll as oppossed to playing everything with a midi keyboard, it's an invaluable tool to quickly audition our compositions and see (hear?) if our chord progressions make sense. It'd be better if the Listen Tool only played the selected notes (the notes we hover the Listen Tool above) for as long as the mouse button is pressed in. FL Studio gets it (you'll hate me for referencing FL so many times, won't you :)
  8. I love the shortcuts manager in Studio One, it's probably one of the best I've seen in a software, but please give us an ability to assign keyboard shortcuts to specific tools. I hate the fact that the keyboard shortcuts 1-6 are different in the Arranger and in the Piano Roll. I would love to assign shortcuts to specific tools, e.g., 1 is always the "Arrow tool", 2 is always the "Slice tool", as opposed to assigning them to "the first tool" or "the second tool" (and so on) when the order is slightly different depending on whether we're inthe Arranger or in the Editor. Pressing a number on the keyboard gives us a different tool in different places within Studio One and that's not optimal.
  9. To take the above a step further, a nice-to-have would be an ability to personalize/change modifier key behavior (shift, ctrl/cmd, alt/option), i.e., reassign zooming in/out from CTRL/CMD+scroll to something else - or - scrolling along the arranger from SHIFT+scroll to something else. I can't be the only person who uses multiple other applications, and not just Studio One, and they all use different modifier keys to do the very same things. E.g., zooming in using ALT+scroll instead of CTRL+scroll would be a welcome feature, or whatever we, users, feel like. Something worth looking into. Presonus are actually great at user experience and there are many pure genius solutions in Studio One. I'm sure they can figure this one out too!
  10. A major update to sampling features, especially in Sample One and Impact XT is well overdue. Studio One seems to be taking a lot of inspiration from Logic Pro X (including the looping feature now too) and this is where Presonus should look for inspiration on sampling as well. Logic's own Sampler and its slicing features. Or Serato Sample for that matter.

This is not a rant. It's a love letter to Studio One (I don't mean to sound corny lol).

Top Comment: I agree with all your points. And for me, every one of the problems listed was solved moving to Reaper, so that's where I'll stay for a while until Studio One has an update that appeals to me again. Another suggestion that I've been asking for, for years, is the ability to keep the playhead/cursor centered during playback. This means that the playhead/cursor stays in the middle of the screen, and the arrangement itself smoothly scrolls from left to right. I know you joked about the FL comparisons, but again... that does it lol, considering this update was aimed at producers and beatmakers, I think it would make sense to be included. I often show my process or audition my songs while streaming, and I've gotten comments on how disorienting it is to have the screen suddenly "jump" to the next part of the composition in S1. Also: still no fade options on Sample One or Impact, in 2024, come on man lol

Forum: r/StudioOne

Why is FL Studio not considered a professional DAW to a lot of people?

Main Post:

I was reading a book on mixing and the author had a section mentioning multiple DAWs and which one to choose/which was the most widely used and professional. This book (copyright 2016) had at least 20 listed and FL Studio wasn't even mentioned, despite having plenty of other small or rarely used DAWS. It did make me think about how many different "professionals" and studios don't tend to use FL and prefer Pro Tools, Logic, Ableton, etc. Is it missing a lot of important features that these other DAWS have? I've been using it for about 2 years now and it works great for everything I have ever needed (making beats and compositions, recording guitars and vocals, and others. Just curious to hear everyone's thoughts on this.

Top Comment: I figure it's really just some leftover misconceptions from the early 2000s. Back when FL was first released (then called FruityLoops) it was essentially just a sequencer with some synths, samples, and basic effects - to the working engineers who needed a fully-functioning DAW, it was sort of seen as a toy, I suppose. And unfortunately, that reputation just kind of... stuck. Obviously all that robust functionality came quickly to later versions (particularly around the rebrand) but they've never been able to quite shake it. I suspect it also being cheap and also super fucking easy to pirate back in the day might have contributed to it being seen as "unserious."

Forum: r/WeAreTheMusicMakers